Digitized document circulating system with circulation history

ABSTRACT

A digitized document circulating system includes a unit provided in a transmission source of a digitized document and for sending the digitized document, a unit for delivering the digitized document to a transmission destination to thereby circulate the digitized document, a unit provided in the transmission destination and for receiving the digitized document, a unit operated by the delivery unit and for obtaining a circulation history containing delivery time, an identifier of the digitized document, the transmission source and the transmission destination, a unit for reading the circulation history and transferring the circulation history to a requester in response to a request for the circulation history issued from the requester, and a unit for displaying the circulation history received.

This is a continuation of application Ser. No. 08/531,401, filed Sep.21, 1995 now U.S. Pat. No. 5,767,847.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a digitized document circulating systemand particularly relates to a digitized document circulating system inwhich when a digitized document prepared for circulation is read by auser, the user can receive history information of a plurality of otherdigitized documents relevant to the digitized document read by the user.

2. Description of the Related Art

As the prices of personal computers, word processors, or the like, falldown, a large number of office workers try to generate documents ortables in the form of digitized documents. To attain an improvement inproductivity of such office workers, there has been made greater thedemand for a digitized document circulating system in which group workof office workers in practical business is modeled as a flow (businessprocess) of documents along a circulation path so that digitizeddocuments are automatically circulated along the circulation path.

Such a system has been disclosed in U.S. patent application Ser. No.08/531,652, filed simultaneously with this application on Sep. 21, 1995.the disclosure of that application is incorporated herein by reference.

If, in group work of office workers using the aforementioned system,each user merely independently goes on with work (processing ofdigitized documents circulated) assigned to the user, the independentwork may hinder the group work. One of important points for animprovement in productivity is that each user performs his or her dutywhile grasping the total image of group work by understanding thesignificance of assigned work (what path is used for circulating thework) and following up already processed work (how the work progressesafter that) by reference to a history of work of related workers, thatis, by reference to a history of circulated digitized documents.

Electronic mail is known as a simple group work system. In theelectronic mail system, messages (a kind of digitized document) aretransmitted/received through a network system between computers. Asdescribed in “UNIX WHITE BOOK, stationary UNIX” (pp.87-98, written byShuichi Yukita and published by McGraw-Hill, Inc., Jul. 30, 1992), adestination (an example of the simplest circulation path) and historyinformation (record of circulation of electronic mail) including thesending time, the sender's name, the receiving time, the receiver's nameand the title, are inserted as additional information in front of thebody of a message. A receiver can know the history of the electronicmail on the basis of this additional information.

In the “method for confirming and controlling transmission of aplurality of electronic mail objects” disclosed in JP-A-2-184142, thefollowing functions have been disclosed in addition to theaforementioned electronic mail function.

(1) A function for storing a copy of a transmitted electronic mail as asender side log;

(2) A function for sending an electronic mail for confirmation from areceiver back to the sender when the receiver receives an electronicmail; and

(3) A function for sending an electronic mail again from the sender tothe receiver when no electronic mail for confirmation is sent in apredetermined time.

According to the technique of JP-A-2-184142, the receiver can procurethe history of a electronic mail and the sender can confirm the arrivalof a electronic mail.

In the “office information processing system” disclosed in JP-A-5-63728,the following functions are provided in addition to the aforementionedelectronic mail function and the functions described in JP-A-2-184142.

(1) A function in which the transmission side of a electronic mailinquires of the reception side about the state of processing of anelectronic mail; and

(2) A function in which the reception side replies to the inquiry of(1).

According to JP-A-5-63728, the receiver can procure the history of anelectronic mail and the sender can also procure the state of processingof an electronic mail on the reception side.

In transactions subjected to the aforementioned digitized documentcirculating system, there are a lot of transactions in which a pluralityof digitized documents are circulated in a manner so that they arecirculated parallelly through different paths respectively and arecollected to one place at a certain point of time. For example, there issuch a transaction that in an ordering transaction, a decision documentand an order document are generated by the planning department and theresearch department respectively and separately, but those documents arecollected into one as an order sheet to obtain permission of theaccounting department's manager and then an ordering slip is issued fromthe material department. In such a transaction, the efficiency forfulfilling the transaction is improved if a user can refer to thehistories of digitized documents which are not passed through the user.For example, the minimum requirement for obtaining permission of theaccounting department's manager is a set of a decision document and anorder document. To fulfill the transaction more smoothly, there isrequired a flexible measure which is such that the planning departmentprocures the history information of the order document from the researchdepartment to check the state of progress of work and the decisiondocument is preferentially generated when the request document has beenhanded to the accounting department's manager.

In the aforementioned conventional technique, however, no considerationis taken of the user's referring to the history information of digitizeddocuments which are not circulated to the user. Hereinafter, a series offlow of digitized documents in a transaction which is made to progressby circulation of the digitized documents among a plurality of users iscalled “transaction”.

An object of the present invention is to provide a digitized documentcirculating system in which users can refer to circulation historyinformation (transaction log) of all digitized documents in one and thesame transaction.

In the aforementioned conventional technique, each user can refer to thestate of processing of processed digitized documents by using thehistories (user log) of the digitized documents circulated to the user,but the user cannot refer to the state of processing of digitizeddocuments not circulated to the user.

Another object of the present invention is to provide a digitizeddocument circulating system in which each user can refer to the state ofprocessing of all digitized documents contained in a transaction byusing a user log.

The present invention provides a digitized document circulating systemin which when a digitized document is transferred, the circulationhistory of a transaction concerning the digitized document is procuredso that the circulation history is displayed for the user in response toan order from the user.

Further, the present invention provides a digitized document circulatingsystem in which a user log is displayed so that circulation historiesconcerning digitized documents assigned from the user log are displayedfor users.

Digitized documents to be circulated and transactions are stored in acondition that they are correlated with each other, so that when adigitized document is transferred, the circulation history of atransaction concerned with the digitized document can be accessed.Accordingly, the circulation history of a concerned transaction can beprocured whenever a digitized document is transferred, so that thecirculation histories of transactions can be accumulated.

Because the user log records the histories of all digitized documentscirculated to users, the circulation history of a transaction concernedwith a specific digitized document can be accessed by displaying theuser log and designating the specific digitized document.

BRIEF DESCRIPTION OF THE DRAWINGS

Further objects, features and advantages of the present invention willbecome more clear from the following detailed description of a preferredembodiment, described with respect to the accompanying drawing.

FIG. 1 is a conceptual view of a business process definition, that is,“Definition of Transaction Process for Ordering Research Materials”;

FIG. 2 is a configuration diagram of a digitized document circulatingsystem according to the present invention;

FIG. 3 is a configuration diagram of a server 211 of FIG. 2;

FIG. 4 is a configuration diagram of a user terminal 212 of FIG. 2;

FIG. 5 is a configuration diagram of a circulation control object block333 stored in a storage unit 330 depicted in FIG. 3;

FIG. 6 is a view showing an example of data contained in a digitizeddocument object “decision document 0705 (523)” depicted in FIG. 5;

FIG. 7 is a view showing an example of data contained in a digitizeddocument object “order document 0705 (524)” depicted in FIG. 5;

FIG. 8 is a view showing an example of data contained in a user object“user C (513)” depicted in FIG. 5;

FIG. 9 is a view showing an example of data contained in a transactionfolder object “research material order 0705 (532)” depicted in FIG. 5;

FIG. 10 is a view showing an example of data contained in a requeststack object 571 depicted in FIG. 5;

FIG. 11 is a view showing an example of data contained in a transactionlog object “log research material order 0705 (562)” depicted in FIG. 5;

FIG. 12 is a view showing an example of data contained in a user logobject “log user C (553)” depicted in FIG. 5;

FIG. 13 is a view showing an example of data contained in a businessprocess definition object “research material request transactiondefinition (541)” depicted in FIG. 5;

FIG. 14 is a configuration diagram of a processing program block 331depicted in FIG. 3;

FIG. 15 is a PAD view of a circulating main program 1410 in FIG. 14;

FIG. 16 is a PAD view of a request stack object reading program 1411 inFIG. 14;

FIG. 17 is a PAD view of a digitized document object delivery program1412 in FIG. 14;

FIG. 18 is a PAD view of a transaction log object updating program 1413in FIG. 14;

FIG. 19 is a PAD view of a transaction log object deleting program 1414in FIG. 14;

FIG. 20 is a PAD view of a terminal processing program 431 in FIG. 4;

FIG. 21 is a view of a first example of display on a display unit 443 inFIG. 4;

FIG. 22 is a PAD view of a request stack object writing process 2063 inFIG. 20;

FIG. 23 is a view of a second example of display on the display unit 443in FIG. 4;

FIG. 24 is a view of an example of data in a digitized document-sortedtransaction log. “log research material order transaction 0705 (decisiondocument 0705)”; and

FIG. 25 is a view of another example of data in a digitizeddocument-sorted transaction log “log research material order transaction0705 (decision document 0705)”.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT (1) Configuration ofDigitized Document Circulating System

FIG. 2 is a schematic view of a digitized document circulating system asan embodiment of the present invention. The digitized documentcirculating system 201 comprises a server 211 for managing andcirculating digitized documents, user terminals 212 to 217 in whichusers process the digitized documents circulated by the user, and anetwork system 218 for connecting the server 211 to the user terminals212 to 217. The user terminals 212 to 217 are respectively assigned tousers A to F of this system. Although FIG. 2 shows 6 terminals as anexample, the number of terminals is not limited to 6. For example, oneuser may use a plurality of user terminals or one user terminal may beshared by a plurality of users.

As will be described later in detail, this digitized documentcirculating system is roughly designed so that users receive digitizeddocuments, edit the digitized documents and pass the digitized documentson to the next through user terminals 212 to 217 whereas the server 211transmits the digitized documents designated by the users, successively.

FIG. 3 shows the configuration of the server 211. The server 211includes a storage unit 330, a central processing unit 320, and anetwork connection unit 310. The storage unit 330 stores a processingprogram block 331 in which a procedure for processing circulation ofdigitized documents is described, a circulation control data block 332composed of a plurality of control data required for user management anddigitized document circulation, and a digitized document block 333composed of a plurality of digitized documents to be circulated. Thecentral processing unit 320 reads a processing program from theprocessing program block 331 and performs digitized documentcirculation. The network connection unit 310 connects the user terminals212 to 217 and the server 211 through the network system 218 so thatdata are transmitted/received between the server 211 and the userterminals 212 to 217.

FIG. 4 shows the general configuration of a user terminal 212. A storageunit 430 includes a processing program 431 in which a procedure forprocessing a digitized document circulated is described, a circulationobject work area 433 which is an area for copying an object transmittedfrom the server, that is, copying a digitized document in order to referto or edit the circulation object; and an application program area 432for referring to and editing the circulation object. A processing unit420 reads a processing program 431 from the storage unit 430 andperforms terminal processing. A network connection unit 410 connects theuser terminal 212 and the server 211 through the network 218. A userinterface 440 feeds an input from a keyboard 441 or a mouse 442 to theprocessing unit 420. A display unit 443 displays processing results ofthe processing unit.

(2) Data Stored in Storage Unit 330 of Server 211

Next, data stored in the storage unit 330 of the server 211 will bedescribed in detail with reference to FIGS. 3 and 5. Hereinafter “block”means an area which is contained in the storage unit 330 and in whichthe same kind of data (objects) are stored.

(2-1) Circulation Object Block

The circulation object block 333 shown-in FIG. 3 is composed of aplurality of circulation objects which are circulated to users. The“circulation object” means a digitized still image, an animation image,a voice, a text or a combination thereof.

(2-2) Circulation Control Data Block

The circulation control data block 332 of FIG. 3 is composed of objectblocks shown in FIG. 5.

The user object block 510 is composed of user objects containing userinformation assigned to users A to F, respectively.

The business process definition object block 540 is composed of businessprocess definition objects which is a script in which business processdefinitions are described. A business process definition object“research material order transaction definition 541” defines a digitizeddocument circulating transaction shown in FIG. 1.

The transaction folder object block 530 is composed of transactionfolder objects which are information for managing all digitized documentobjects of transactions in a business process defined by the businessprocess definition. The transaction folder objects 531 to 533 areassigned to transactions 0704, 0705 and 0706. The transaction folder hasa function for generally managing a plurality of digitized documentobjects.

The digitized document object block 520 is composed of digitizeddocument objects which are management information for circulating one ora plurality of circulation objects as one digitized document. Thedigitized document objects 521 and 522 are circulated in a transaction“research material order transaction 0704”, the digitized documentobjects 523 and 524 are circulated in a transaction “research materialorder transaction 0705”, and the digitized document objects 525 and 526are circulated in a transaction, “research material order transaction0706”.

The manager object block 570 has a request stack object 571 which is adata object for controlling the whole of the digitized documentcirculating system. The request stack object is a first-in first-outstack for storing the name of a digitized document object requested by auser to be transferred.

The transaction log object block 560 which is characteristic of thepresent invention has transaction log objects in which the circulationhistory of all digitized documents contained in the transactions, thatis, the circulation history of all digitized document objects managed bythe transaction folders is stored. The transaction log objects 561 to563 relate to the transactions “research material order transaction0704”, “research material order transaction 0705”, and “researchmaterial order transaction 0706”, respectively.

The user log object block 550 are composed of a plurality of objectscontaining user logs of users A 551 to F 556.

FIG. 6 shows the details of the digitized document object “decisiondocument 0705 (523)”.

The item “circulation object list” is a name list of circulation objectsmanaged by the digitized document object “decision document 0705 (523)”.

The item “digitized document type” is a name which is used in businessprocess definition in order to define the type of the digitized documentto be circulated. The item value “decision document” corresponds to“decision document 111”.

The item “owner” is the name of a current user which uses the digitizeddocument object.

The item “transaction object” is the name of a transaction folder objectwhich manages the digitized document object. The digitized documentobject 523 is managed by the transaction folder object 532.

FIG. 7 shows the details of a digitized document object “order document0705 (524)”. Here, the “order document 0705” is an identifier of thedigitized document.

The item “circulation object list” is a list of names of circulationobjects managed by the digitized document object “decision document 0705(524)”. The circulation objects contain a text “order0705.txt” and a bitmap data “order0705.bmp”.

The item “digitized document type” is the name of the type of thedigitized document to be circulated. For example, the item value is“order document” 112 (FIG. 1).

The item “owner” is the name of a current user which uses the digitizeddocument object. For example, the item value is “user C”.

The item “transaction object” is the name of a transaction folder objectwhich manages the digitized document object. The item value “researchmaterial order transaction 0705 (532)” indicates the fact that thedigitized document object is managed by the transaction folder object“research material order transaction 0705 (532)”.

The digitized document object “decision document 0705 (523)” and thedigitized document object “order document 0705 (524)” are both managedby the transaction folder object “research material order 0705 (532)”.

FIG. 8 shows the details of a user object “user C (513)” as an exampleof the user object.

The item “user” is the name of a user which is a subject of the userobject. The item value “user C” indicates the fact that the user object“user C (513)” is the user object of the user C.

The item “user log object” is the name of a user log object concerningthe user C who uses the user object “user C (513)”. The item value “loguser C” indicates the fact that the user log object having the user logof the user C using the user object “user C (513)” is the user logobject “user C (553)”.

The item “belonging digitized document object list” means a list ofdigitized document objects circulated to the user C.

FIG. 9 shows the detail of a transaction folder object “researchmaterial order 0705 (532)” as an example of the transaction folderobject.

The item “business process definition object” is the name of a businessprocess definition object by which a business process for defining atransaction requiring circulation of digitized document objects managedby the transaction folder object is defined. The item value “researchmaterial order transaction definition” indicates the fact that thebusiness process definition object for defining a transaction requiringcirculation of digitized document objects managed by the transactionfolder object “research material order 0705 (532)” is the businessprocess definition object “research material order transactiondefinition 541”.

The item “management digitized document object list” is a list of namesof digitized document objects managed by the transaction folder object.The item value “{decision document 0705, order document 0705}” indicatesthe fact that digitized document objects managed by the transactionfolder object are “decision document 0705 (523)” and “order document0705 (524)”.

The item “transaction log object” is the name of a transaction logobject for procuring a transaction log which is the circulation historyof digitized documents object managed by the transaction folder object.The item value “log research material order 0705” indicates the factthat the transaction log object concerning the transaction folder objecthas an identification “log research material order transaction 0705(562)”.

In FIG. 9, the transaction folder object “research material order 0705(523)” manages digitized document objects “decision document 0705 (523)”and “order document 0705 (524)” circulated on the basis of the businessprocess definition object “research material order transactiondefinition (541)”. The circulation history of the digitized documentobjects “decision document 0705 (523)” and “order document 0705 (524)”is stored as the item value “log research material order transaction0705 (562)” in the transaction log object.

FIG. 10 shows the detail of a request stack object 571. The item “queuedigitized document object” is the name of a digitized document objectwritten in the request stack object 571 by the user terminal. The itemvalue “none” indicates the fact that there is no digitized documentobject name written in the corresponding request number. The item“request number” is the request order number of a queue digitizeddocument object. As will be described later in detail, the request stackis a definite stack of first-in firstout, and the request number isprovided for first-in first-out control. The request stack object shownin FIG. 10 indicates the fact that digitized document objects “orderdocument 0705 (524)” and “order document 0706 (526)” are queue digitizeddocument objects.

As an example of a transaction log object which is characteristic of thedigitized document circulation system provided by the present invention,a transaction log object “log research material order 0705 (562)” isshown in detail in FIG. 11. History data which are procured as atransaction log are composed of time, digitized document object, source,and destination. The transaction log object is formed by arranging thesehistory data in time sequence. The item “source” indicates the name of auser which requests sending (circulation) of a digitized documentobject. The item “destination” indicates the name of the next user towhich the digitized document object is. circulated. The item “digitizeddocument object” indicates the name of the digitized document object tobe sent. The item “time” indicates a point of time of sending.

FIG. 12 shows a user log object “log user C (553)” as an example of theuser log object. History data procured as a user log are composed oftime, digitized document object, and operation. The user log object isformed by arranging these history data in time sequence. “Receive” or“send” is recorded in the item “operation”. The “receive” indicates thefact that the digitized document is received. The “send” indicates thefact that the digitized document is required to be sent. The item“digitized document object” indicates the name of the digitized documentobject to be sent. The item “time” indicates a point of time of carryingthe operation.

FIG. 13 shows in detail the description of the business processdefinition object “research material order transaction definition 541”.The interpretation of the description will be described later.

(2-3) Processing Program Block

As shown in FIG. 14, the processing program block 331 is composed of acirculating main program 1410 for expressing the outline of circulation,a request stack object reading program 1411 for expressing a procedureof reading the request stack object 571, a digitized document objecttransferring program 1412 for expressing a procedure of transferring thedigitized document object, a history procuring program 1413 forexpressing a procedure of procuring a transaction log and a user log,and a transaction log deleting program 1414 for expressing a procedureof deleting a transaction log object. These programs will be describedlater.

(3) Data stored in Storage Unit 430 of User Terminal 212

As shown in FIG. 4, a processing program 431, an application programarea 432 and a circulation object work area 433 are stored in thestorage unit 430.

(3-1) Processing Program 431

A procedure of processing in a user terminal is described in theprocessing program which will be described later.

(3-2) Application Program Block 432

The block contains an application program for editing the digitizeddocument, such as a word processor, or the like.

(3-3) Circulation Object Work Area 433

This is a storage area in which the circulation object stored in thecirculation object block 333 of the server 211 is copied to the storageunit 430 of the user terminal 212 through the network system 218 inorder to edit the circulated object by using the application program.The edition of the circulation object in the user terminal 212 isperformed by editing a copy of the circulation object in the circulationobject work area 433. After the edition, the circulation object isupdated by overwriting the edited copy on the circulation object storedin the circulation object block 333 of the server 211 through thenetwork system 218.

(4) Description of Digitized Document Circulating Procedure (4-1)Outline of Circulating Transaction

First, the digitized document circulating transaction will be describedin brief.

FIG. 1 shows a flow of research material order transaction to beprocessed. Users A (101) to F (106) include processes performed by userterminals, and processes in which users A to F receive digitizeddocuments, edit the digitized documents and send the digitized documentsto the next user by operating user terminals. The arrows connecting theusers A (101) to F (106) express a flow of digitized documentcirculation. The server 211 transfers a digitized document requested tobe sent by a user located in the start of each arrow to a user locatedin the end of the arrow. The “decision document” 111 and “orderdocument” 112 located on each arrow are digitized documents transferredalong the arrow.

A flow of the research material order transaction will be describedbelow. To start the research material order transaction, the user A 101requests the sending of two digitized documents, that is, the “decisiondocument” 111 and “order document” 112 from the user terminal. Theserver 211 delivers one digitized document, that is, the “decisiondocument” 111 to the user B (102) and delivers the other digitizeddocument, that is, the “order document” 112, to the user C (103).

The user B (102) edits the digitized document received from the user A(101) by using an application program in the user terminal to therebycomplete the digitized document and requests the server 211 to transferthe thus edited digitized document. The server 211 delivers thedigitized document to the user E (105).

The user C (103) inputs data of the digitized document received from theuser A (101) by using an application program in the user terminal and,after completion of input, requests the server 211 to transfer thedigitized document. The server 211 delivers the digitized document tothe user D (104).

The user D (104) checks the digitized document received from the user C(103) by using an application program in the user terminal and requeststhe server 211 to transfer the thus checked digitized document aftercompletion of the check. The server 211 delivers the digitized documentto the user E (105).

After reception of the two digitized documents from the users B (102)and D (104) respectively, the user E (105) makes a decision by using anapplication program in the user terminal and requests the server 211 totransfer the digitized documents. The server 211 delivers the digitizeddocuments to the user F (106) which will perform ordering.

The user F (106) performs ordering by using an application program inthe user terminal on the basis of the digitized documents, that is, the“decision document” 111 and “order document” 112 received from the userE 105. When ordering is completed, this transaction is finished.

A business process definition, for example, business process definitionobject “research material order transaction definition (541)” expressesthe aforementioned flow of delivery of digitized documents. The term“transaction”, for example, “research material order transaction 0705”means a series of procedures for research material order transaction.

(4-2) Circulation Procedure

The procedure of circulating digitized documents is described inprocessing programs contained in the processing program block 331 of theserver 211 and the processing program area 431 of each user terminal.

(4-2-1) Digitized Document Circulating Procedure in Server

The digitized document circulating procedure in the server 211 is aprocedure for transferring digitized documents from user to user. Thisprocedure is stored as a processing program in the processing programblock 331. The request stack object reading program 1411, the digitizeddocument object transferring program 1412, the history procuring program1413 and the transaction log deleting program 1414 are sub-routines ofthe circulating main program 1410. Description will be made along theprocedure of the circulating main program 1410 inclusive of thedescription of these sub-routines.

A procedure shown in the PAD view of FIG. 15 is described in thecirculating main program 1410. In step 1510, the procedure of thecirculating main program starts. In step 1511, the procedure in andafter step 1520 is repeated unless a termination instruction is givenfrom the user terminal. When the termination instruction is given fromthe user terminal, the situation of the routine goes to step 1512. Inthe step 1512, the procedure of the circulating main program isterminated. In the step 1520, a request stack object 571 is read.

FIG. 16 is a PAD view showing a procedure of reading the request stackobject 571. In step 1610, the procedure of reading the request stackobject starts. In step 1611, a queue digitized document object of therequest number 1 is read as a result of reading. When the queuedigitized document object of the request number 1 is “none” in step1612, the procedure in and after step 1620 is carried out. Otherwise inthe step 1612, the procedure in and after step 1630 is carried out. Inthe step 1620, the result of reading is regarded as “none” and therequest stack object reading procedure is terminated. The request stackobject is a first-in first-out stack. In the procedure of steps 1630 to1662, the stack of the request number 1 is cleared and data in the stackis shifted. In the step 1630, a judgment is made as to whether themaximum stack number n_max of request stack objects is 1 or not(n_max≧1). In the case of n_max=1, the procedure in and after step 1640is carried out. In the case of n_max>1, the procedure in and after step1650 is carried out. In the step 1640, “none” is written in the queuedigitized document object of the request number 1 and then the situationof the routine goes to step 1641. In the step 1641, this request stackobject reading procedure is terminated. In the step 1650, the initialvalue of n which is a counter variable for the request number is setto 1. In step 1651, the procedure in and after step 1660 is carried outunless n=n_max is valid or the queue digitized document object of therequest number (n+1) is “none”. When n=n_max is valid or when the queuedigitized document object of the request number (n+1) is “none”, thesituation of the routine goes to step 1652. In the step 1652, therequest stack object reading procedure is terminated. In the step 1660,the queue digitized document object of the request number (n+1) isoverwritten onto the queue digitized document object of the requestnumber n and then the situation of the routine goes to step 1661. In thestep 1661, “none” is overwritten onto the queue digitized documentobject of the request number (n+1). In step 1662, n is increased by 1.Thus, the request stack object 571 is read out by the aforementionedprocedure.

In the case of the request stack object shown in FIG. 10, the digitizeddocument object “order document 0705” of the request number 1 is readout. When the reading of the request stack object is completed, “orderdocument 0705” is obtained as a reading result.

Returning to the description of FIG. 15, when the result of reading ofthe request stack object is not “none” in step 1521, the procedure inand after step 1530 is carried out. When the result of reading of therequest stack object is contrariwise “none”, the procedure of the step1521 is terminated and the situation of the routine goes to step 1511.In the step 1530, a queue digitized document object is procured from thedigitized document object name read in the step 1520. In step 1531, thename of an owner and the name of a transaction folder object areprocured from the digitized document object procured in the step 1530.Because the owner is a user requesting the server to transfer thedigitized document object to the next user, it is said that the owner isa source of the digitized document object. In step 1532, a transactionfolder object is procured from the transaction folder object nameprocured in the step 1531. In step 1533, the name of a business processdefinition object is procured from the transaction folder objectprocured in the step 1532. In step 1534, a business process definitionobject is procured from the business process definition object nameprocured in the step 1533. As described above, in the case of therequest stack object shown in FIG. 10, “order document 0705” is obtainedas a result of reading. From the digitized document object “orderdocument 0705 (524)”, it is found that the owner is “user C”, thetransaction folder object is “research material order 0705 (562)” andthe business process definition object is “research material ordertransaction definition 541”. In step 1535, the destination of thedigitized document object is obtained by examining the business processdefinition object procured in the step 1534.

A business process definition is constituted by a combination of scriptsas follows.

#current user name (owner name)

proc(

type(digitized document type name),

next(next owner name)

)

The source of the digitized document object is described as owner nameof the digitized document object after #. Description about onedigitized document type is bracketed in proc( ). The digitized documenttype is described in type( ), and the name of a user which is thedestination of the digitized document object is described in next( ).

Here, the method of interpreting the business process definition objectwill be described with reference to FIG. 12 taking as an example thebusiness process definition object “research material order transactiondefinition (541)” shown in FIG. 13. Here, the owner name BP_START meansa start point of a business process, and BP_END means an end pointthereof. Because the owner of the digitized document object “orderdocument 0705(524)” is user C (103), the place of #user C in thebusiness process definition object is first examined. In the place of#user C, it is found from the description in the place bracketed inproc( ) that a digitized document object of a digitized document type“order document” is delivered to user D (104) who is the next user.

Returning to the description of FIG. 15, in step 1536, the digitizeddocument object is delivered to the next user obtained in the step 1535.After delivery, the situation of the routine goes to step 1537.

FIG. 17 is a PAD view showing the digitized document object transferringprocedure of the step 1536. Here, the procedure of transferring adigitized document object “order document 0705(524)” from user C who isthe current owner to user D who is the next owner will be described withreference to FIG. 17. In step 1710, the digitized document objecttransferring procedure starts and the situation of the routine goes tostep 1711. In the step 1711, the owner of the digitized document objectto be transferred is changed from the current owner to the next ownerobtained in the step 1535 and then the situation of the routine goes tostep 1712. Here, the owner of the digitized document object “orderdocument 0705(524)” is changed from user C to user D. In the step 1712,the name of the digitized document object is deleted from the ownerdigitized document object list in the user object of the current ownerand then the situation of the routine goes to step 1713. Here, “orderdocument 0705” is deleted from the owner digitized document object listin the user object “user C (513)”. In the step 1713, a log is added tothe user log object of the current owner and the situation of theroutine goes to step 1714. Here, a log “Jul. 6, 1994 16:45” indicatingthe current time 16:45 Jul. 6, 1994 is added as time to the user logobject “log user C (553)” of the user C (103);

a log “request document 0705” is added as a digitized document object;and a log “send” is added as an operation. In the step 1714, the name ofa digitized document object to be transferred is added to the ownerdigitized document object list in the user object of the next owner andthe situation of the routine goes to step 1715. Here, “order document0705” is added to the owner digitized document object list in the userobject “user D (514)”. In the step 1715, a log is added to the user logobject of the next owner and the situation of the routine goes to step1716. Here, a log “Jul. 6, 1994 16:45” indicating the current time16:45Jul. 6, 1994 is added as time to the user log object “log user C(554)” of the user D; a log “order document 0705” is added as adigitized document object; and a log “receive” is added as an operation.In the step 1716, the digitized document object transferring procedureis terminated. By the aforementioned procedure, the digitized documentobject transferring process 1536 is performed.

Returning to the description of FIG. 15, in the step 1537, thetransaction log object which is characteristic of the digitized documentcirculating system provided by the present invention is updated and thesituation of the routine goes to step 1538 after the updating of thetransaction log object.

FIG. 18 is a PAD view showing a procedure of updating the transactionlog object. In this embodiment, a transaction log object updatingprocess in the case where a digitized document object “order document(524)” is transferred from user C who is the current owner to user D whois the next user will be described with reference to FIG. 18. In step1810, the transaction log object updating process starts. In step 1811,the name of a transaction log object is procured from the transactionfolder object. Here, the transaction log object name “log researchmaterial order 0705” is procured from the transaction folder object“research material order 0705 (532)” of the digitized document object“order document 0705 (524)” obtained in the step 1532. In step 1812, atransaction log object is procured from the transaction log object nameobtained in the step 1811. Here, the transaction log object “logresearch material order 0705 (562) is obtained. In step 1813, a log isadded to the transaction log object. Here, a log “Jul. 6, 1994 16:45”indicating the current time 16:45 Jul. 6, 1994 is added as time to thetransaction log object “log research material order 0705 (562)”; a log“order document 0705” is added as a digitized document object; a log“user C” is added as the source; and a log “user D” is added as thedestination. In the step 1814, the transaction log object updatingprocess is terminated. By the aforementioned procedure, the transactionlog object updating process 1537 is performed.

Incidentally, the server 211 procures the name of a source user and thename of a destination user from the digitized document object of thesource and the digitized document object of the destination by aprocessing program not shown. Further, the server 211 procures userobjects corresponding to the user names and procures user log objectnames from these user objects and updates user log objects correspondingto the user log object names.

In the step 1538 shown in FIG. 15, the transaction log deleting processwhich is characteristic of the present invention is carried out. FIG. 19is a PAD view showing a transaction log deleting procedure.

In step 1910, the transaction log object deleting process starts and thesituation of the routine goes to step 1911. In the step 1911, the sourceof the digitized document object transferred in the step 1536 isexamined so that a judgment is made as to whether the digitized documentobject has reached the end point of the business process definition ornot. Because the digitized document object has not reached the end pointof the business process definition when the destination is BP_END, theprocedure in and after step 1920 is carried out. When the destination isBP_END, the procedure of step 1912 is carried out. In the step 1912, thetransaction log object deleting process is terminated. In the step 1920,the name of the digitized document object is deleted from the managementdigitized document object list of the transaction folder object whichmanages the digitized document object transferred in the step 1536. Instep 1921, a judgment is made as to whether the management digitizeddocument object list of the transaction folder object managing thedigitized document object transferred in the step 1536 is empty or not.Only the names of digitized document objects currently used forcirculation are stored in the management digitized document object list.By examining whether the management digitized document object list isempty or not, a judgment can be made as to whether the circulation ofall digitized document objects managed by the transaction folder objectis completed or not. When the list is not empty, the procedure of step1922 is carried out. When the list is empty, the procedure in and afterstep 1930 is carried out. In the step 1922, the transaction log objectdeleting process is terminated. In the step 1930, the transaction logobject is deleted. In step 1931, the transaction log object deletingprocess is terminated.

By the aforementioned procedure, the transaction log object is deletedwhen the circulation of all digitized document objects managed by thetransaction folder object is terminated. The termination of thecirculation of all digitized document objects managed by the transactionfolder object indicates the fact that the transaction is finished.Because the significance of the transaction log is considered to belowered as the transaction is finished, the useless transaction logobject is deleted to save the storage capacity.

(4-2-2) Digitized Document Circulating Procedure in User Terminal

The digitized document circulating procedure in a user terminal isdescribed in the processing program 431. The procedure shown in the PADview of FIG. 20 is described in the processing program 431. In step2010, the terminal processing program starts and the situation of theroutine goes to step 2011. In the step 2011, success of log-in (processof inputting user name and password through the keyboard) of the user tothe user terminal is waited for. When the log-in results in success, thesituation of the routine goes to step 2012. Here, description will bemade upon the assumption that the user C makes log-in from the userterminal 212. In the step 2012, lines of the user terminal 212 and theserver 211 are first connected by using the terminal network connectionunit 410 of the user terminal 212, the network system 218 and thenetwork unit 310 of the server 211. In step 2013, a judgment is made asto whether any user object for the user which made log-in to the userterminal exists in the server 211 or not. When there is no user object,the situation of the routine goes to step 2020 because the user cannotuse the digitized document circulating system. When there is any userobject, the situation of the routine goes to step 2030. Because the userobject “user C (513)” for the user C (103) exists in the user objectblock 510, the procedure in and after the step 2030 is carried out. Inthe step 2020, the line connected in the step 2012 is turned off todisconnect the user terminal from the server. In step 2021, the terminalprocessing program is terminated. In the step 2030, the content of theuser object is procured from the server 211 through the network system218. Now, assume that the user object “user C (513)” is procured. Instep 2031, the content of the user object procured in the step 2030 anda processing menu to the user are displayed on the display unit 443.

FIG. 21 shows an example of display. A menu for processes in the userterminal is displayed on a display area 2110. By clicking a mouse 442 onone of buttons 2111 to 2115, an instruction to execute a functionassigned to the button can be given to the processing unit 420 throughthe user interface connection unit 440. A function of unsealing thecirculated digitized document object is assigned to the unsealing button2111; a function of requesting the sending of the digitized document isassigned to the sending button 2112; a function of displaying thetransaction log is assigned to the transaction log display button 2113;a function of terminating the user terminal 212 is assigned to the userterminal termination button 2114; and a function of terminating theserver 211 and the user terminal 212 is assigned to the digitizeddocument circulation termination button 2115. The name of the user whichcurrently uses the user terminal is displayed on a display area 2120.Now, “user C” is displayed. As digitized documents possessed by theuser, the names of digitized document objects contained in the ownerdigitized document object list in the user object are displayed on adisplay area 2130. An input area 2131 is an area in which the userdesignates or inputs the number displayed together with the name of adigitized document object by using the keyboard 441 so that thedigitized document object to be subjected to terminal processing isselected from the digitized document object names displayed on thedisplay area 2130. As the work history of the user, user log objects foruser objects are displayed in the form of a table on a display area2141. As for the user log objects, when a procuring request with theuser name is sent from the user terminal to the server 211, the server211 obtains a corresponding user object on the basis of the user name,obtains the name of a corresponding user log object on the basis of theuser object and sends the corresponding user log object to the userterminal. In this embodiment, the log user C (553) of the user logobject is displayed on the basis of the user C (513) of the user object.

Returning to the description of FIG. 20, in the step 2032, inputting theuser's request by using a button is waited for. When the user terminaltermination button 2114 or the circulation termination button 2115 ispushed, the situation of the routine goes to step 2033. When any otherbutton is pushed, the situation of the routine goes to step 2040. In thestep 2033, in the case where as the terminal processing terminationbutton is pushed so that a request to terminate the terminal processingis inputted, the situation of the routine goes to step 2080. When thecirculation button is pushed so that a request to terminate thecirculation is inputted, the situation of the routine goes to step 2090.In the step 2080, the line connected to the server 211 in the step 2012is disconnected and then the situation of the routine goes to step 2081.In the step 2081, the terminal processing program is terminated. In thestep 2090, an instruction to terminate the circulating program isinputted when the circulating main program 1410 of the server 211executes the step 1511, and then the situation of the routine goes tostep 2091. In the step 2091, the line connected to the server 211 in thestep 2012 is disconnected and then the situation of the routine goes tostep 2092. In the step 2092, the terminal processing program isterminated. In the step 2040, processing is branched correspondingly tothe button pushed in the step 2032.

When the unsealing button 2111 is pushed, the situation of the routinegoes to step 2070 so that a digitized document unsealing process iscarried out in steps 2070 and 2071. The digitized document unsealingprocess is a process in which a circulation object as the content of thedigitized document received by the user is copied from the server 211onto the circulation object work area 433 of the user terminal throughthe network system 218 in order to edit the digitized document by usingan application program contained in the application program block 432.

When the sending button 2112 is pushed, the situation of the routinegoes to step 2060 so that a digitized document sending process iscarried out in steps 2060 to 2063. The digitized document sendingprocess is a process in which the name of a digitized document requiredto be sent is written into the request stack object 571 of the server211 so that the digitized document is delivered to the next user inaccordance with the digitized document circulating procedure of theserver 211.

When the transaction log display button 2113 is pushed, the situation ofthe routine goes to step 2050 so that a transaction log display processis carried out in steps 2050 to 2054. The transaction log displayprocess is a process for displaying the transaction log of thetransaction in which the digitized document designated by the user iscirculated.

(4-2-2-1) Digitized Document Unsealing Process

In the step 2070 of FIG. 20, the selection number inputted to the inputarea 2130 by the user is first procured. Then, the name of a digitizeddocument object corresponding to the selection number is procured fromthe digitized document object name list displayed on the display area2131, and then the situation of the routine goes to step 2071. When theselection number corresponding to a digitized document required to beunsealed is inputted to the input area 2130 by the user while referringto the display area 2131, the name of the digitized document objectrequired to be unsealed by the user is obtained in this step. Assumingnow that the user C gives “1” to the display area 2130, then “orderdocument 0705” is obtained as the name of the digitized document objectto be unsealed.

In the step 2071, a digitized document object is procured from thedigitized document object name obtained in the step 2070, so thatcirculation objects in a circulation object list for the digitizeddocument object are copied from the server 211 onto the circulationobject work area 433 through the network system 218, and then thesituation of the routine goes to step 2032.

When the digitized document object name obtained in the step 2070 is“order document 0705”, the digitized document object “order document0705 (524)” is procured and “order0705.txt” and “order0705.bmp” arecopied as circulation objects onto the circulation object work area 433.

After the terminal processing is terminated, the user can edit thecopies of the circulation objects on the circulation object work area433 by using an application program contained in the application programblock 432.

(4-2-2-2) Digitized Document Sending Process

In the step 2060, the selection number inputted to the input area 2130by the user is first procured. Then, the name of a digitized documentobject corresponding to the selection number is procured from thedigitized document object name list displayed on the display area 2131and then the situation of the routine goes to step 2061. When theselection number corresponding to a digitized document requested to besent is given to the input area 2130 by the user while referring to thedisplay area 2131, the name of the digitized document object required tobe sent by the user is obtained in this step. When the user C gives “1”to the display area 2130, “order document 0705” is obtained as the nameof the digitized document object to be sent.

In the step 2061, a digitized document object is first procured from thedigitized document object name obtained in the step 2060, so that thenames of circulation objects constituting the digitized document objectare procured. Then, circulation objects constituting the digitizeddocument are overwritten from the circulation object work area 433 ontothe circulation objects stored in the circulation object block of theserver 211 through the network system 218, and then the situation of theroutine goes to step 2602.

When the digitized document object name obtained in the step 2060 is“order document 0705”, “order0705.txt” and “order0705.bmp” from thecirculation object work area 433 are respectively overwritten onto“order0705.txt” and “order0705.bmp” contained in the circulation objectblock of the server 211. Accordingly, the next user whom the digitizeddocument object “order document 0705 (524)” is circulated receives thedigitized document object order document 0705 (524)” edited by the userC.

In the step 2062, a judgment is made as to whether the request stackobject writing process results in success or not. Unless the requeststack object writing process results in success, the procedure of thestep 2063 is repeated. When the request stack object writing processresults in success, the situation of the routine goes to step 2032.

In the step 2063, the digitized document object name of the digitizeddocument object to be subjected to a sending process is written into therequest stack object 571 of the server 211 and the situation of theroutine goes to step 2062.

Here, FIG. 22 is a PAD view showing the request stack writing process2063. In FIG. 22, n_max is the maximum number of stacks for requeststack objects. In step 2210, the request stack object writing processstarts. In step 2211, the initial value of n which is a variable forcounting the request number is set to “1”. In step 2212, in order toexamine the request number for writing the queue digitized documentobject name, the procedure in and after step 2220 is repeated unless thequeue digitized document of the request number n in the request stackobject 571 is “none”. When the queue digitized document of the requestnumber n in the request stack object 571 is “none”, the situation of theroutine goes to step 2213. In the step 2213, the name of the digitizeddocument object required to be sent is written into the queue digitizeddocument object of the request number n in the request stack object 571.In step 2214, the request stack object writing process is terminated. Inthe step 2220, the situation of the routine goes to step 2230 as long asthe relation n<n_max is valid. When n<n_max is invalid, the situation ofthe routine goes to step 2240. In the step 2230, the request number n isincreased by 1 and the situation of the routine goes to the step 2212.In the step 2240, the request stack writing process is terminatedabnormally (the request stack writing process results in failure)because there is no space for the digitized document to be written inthe request stack.

By the aforementioned process, the digitized document object name of thedigitized document object to be subjected to the sending process iswritten into the request stack object 571 of the server 211. When thedigitized document object name obtained in the step 2060 is “orderdocument 0705” and the request stack object writing process results insuccess, the digitized document object name “order document 0705” sentby the user C is written into the request stack object 571. Thedigitized document object “order document 0705 (524)” in which the nameis written into the request stack object 571 is circulated to the nextuser by a process based on the circulating main program 1410 of theserver 211 as described above.

(4-2-2-3) Transaction Log Display Process

The transaction log display process which is characteristic of thepresent invention will be described below. In step 2050, the selectionnumber given to the input area 2140 by the user is first procured. Then,names of digitized document objects constituting a log corresponding tothe selection number are procured from user logs which are the contentsof user log objects displayed on the display area 2141 and then thesituation of the routine goes to step 2051.

The input area 2140 is an area in which the number displayed togetherwith a log containing the name of a digitized document object isdesignated or inputted by the user through the keyboard 441 so that adigitized document object to be displayed on the transaction log isdesignated from the user log objects displayed on the display area 2141.When the selection number corresponding to a log containing thedigitized document object required for displaying the transaction log isgiven to the input area 2140 by the user while referring to the displayarea 2141, the name of the digitized document object required fordisplaying the transaction log by the user is obtained. The input area2130 may be used in the same manner as in the digitized document objectunsealing process or in the digitized document object sending process sothat the selection number corresponding to the name of a digitizeddocument object currently possessed by the user is designated orinputted by the user. When the user C gives the selection number “2” tothe input area 2140, “order document 0705” is designated as the name ofthe digitized document object for displaying the transaction log.

In step 2051, a digitized document object is first procured from theserver 211 by using the digitized document object name procured in thestep 2050. In the server 211, the digitized document object block 520 issearched for the target digitized document object and the targetdigitized document object is delivered to the user terminal. Then, atransaction folder object for managing the digitized document object isprocured from the server 211 by using the transaction folder name of thedigitized document object. In the server 211, the transaction folderobject block 530 is searched for the target transaction folder objectand the target transaction folder object is delivered to the userterminal. Finally, a transaction log object concerning the transactionfolder object is procured by using the transaction log object name ofthe transaction folder object. In the server 211, the transaction logdesignated is read and delivered to the user terminal. Then, thesituation of the routine goes to step 2052.

When “order document 0705” is designated as the name of the digitizeddocument object for displaying the transaction log in the step 2050, atransaction folder object “research material order 0705 (532)” and atransaction log object “log research material order 0705 (562)” areprocured in this step.

In the step 2052, as exemplified in FIG. 23, the transaction logreceived from the server 211 is displayed in the form of a table on thedisplay area 2310 of the display 413 of the user terminal 212; thedigitized document object name obtained in the step 2050 is displayed onthe display area 2311; the transaction folder name obtained in the step2051 is displayed on the display area 2312; and then the situation ofthe routine goes to step 2053.

When the transaction folder object “research material order 0705 (532)”and the transaction log object “log research material order 0705 (562)”are procured in the step 2051, the transaction log object “log researchmaterial order 0705 (562)” is displayed on the display area 2310; thedigitized document object name “order document 0705” is displayed on thedisplay area 2311; and the transaction object name “research materialorder 0705” is displayed on the display area 2312.

By this process, the user C can procure the transaction log object “logresearch material order transaction 0705 (562)” containing thecirculation history of the digitized document object “order document0705 (524)” circulated to the user C on the basis of the user log object“log user C (553)” displayed on the display area 2141. Because thetransaction log object “log research material order transaction 0705(562)” is the circulation history of the digitized document objects“decision document 0705 (523)” and “order document 0705 (524)” belongingto one and the same transaction, the circulation history of thedigitized document object “decision document 0705 (523)” which is notcirculated to the user C can be provided to the user C.

Although the aforementioned embodiment has shown the case where thetransaction folder name and the transaction log object name are given onthe user terminal side, the present invention can be applied to the casewhere the transaction folder name and the transaction log object nameare procured successively from the server 211 by a sample operation ofinputting the digitized document object name so that the targettransaction log is automatically decided.

In the step 2053, digitized document object names which appear in thetransaction log is first extracted from the transaction log. Then, thetransaction log is sorted by the digitized document object names thusextracted, and then the situation of the routine goes to step 2054. Inthe sorting of the transaction log by the digitized document objectnames, digitized document object names recorded in the transaction logare omitted because they are not necessary. In the case of a transactionlog object “log research material order 0705 (562)”, digitized documentobject names “decision document 0705” and “order document 0705” areextracted, so that transaction log objects are sorted by the digitizeddocument object names, respectively. Digitized document-sortedtransaction logs obtained by sorting the transaction log by thedigitized document object names are shown in FIGS. 24 and 25.

In step 2054, the digitized document-sorted transaction logs aredisplayed and then the situation of the routine goes to step 2032. Inthe case of digitized document-sorted transaction logs shown in FIGS. 24and 25, the digitized document-sorted transaction log based on thedigitized document object “decision document 0705 (523)” is displayed onthe display area 2320 and the digitized document object name “decisiondocument 0705” is displayed on the display area 2321. The digitizeddocument-sorted transaction log based on the digitized document object“order document 0705 (522)” is displayed on the display area 2330 andthe digitized document object name “order document 0705” is displayed onthe display area 2331.

It may be difficult to see the transaction log object “log researchmaterial order transaction 0705 (562)” displayed on the display area2310, because the circulation histories of the digitized documentobjects “decision document 0705 (523)” and “order document 0705 (524)”belonging to one and the same transaction are mixed. Because thedigitized document-sorted transaction logs displayed on the displayareas 2320 and 2330 are obtained respectively by extracting acirculation history concerning a single digitized document object fromthe transaction log object “log research material order transaction 0705(562)”, each history can be presented so that the history can be easilyread by the user who pays attention to a single digitized documentobject. Further, the digitized document-sorted transaction log obtainedby extracting the circulation history concerning the digitized documentobject “decision document 0705 (523)” not circulated to the user C canbe provided to the user C.

Although the aforementioned embodiment has shown the case wherefunctions are assigned to the server 211 and the user terminal 212 asshown in FIGS. 3 and 4, the present invention is not limited thereto.

A first effect of the present invention is that each user of thedigitized document circulating system can procure not only the historyinformation of a digitized document circulated to the user but also thehistory information of another circulated digitized document containedin one and the same transaction of the digitized document circulated tothe user. Hence, the user can make work progress while grasping thestate of circulation of digitized documents contained in a transaction,so that smoother transaction management can be aided. For example, in abusiness process shown in FIG. 1, it is now assumed that the minimumrequirement for the user E (105) making work progress is a set ofdocuments, that is, the “decision document” 111 and “order document”112.

Assume that a transaction log as expressed in the display area 2310 ofFIG. 23 is procured by the user C (103) at 18:00 on Jul. 6, 1994. Theuser C (103) can know the fact that about 3 hours is passed after adigitized document, that is, the “decision document 0705” not circulatedto the user C (103) has been already circulated to the user E (105).Accordingly, the processing of a digitized document “order document0705” assigned to the user C can be preferentially hastened, so that thebusiness process can be smoothened as a whole. Because in this mannerone business process is managed more efficiently by such group work of aplurality of persons, a flow of the business process as a whole can begrasped while a user sees not only the state of process of a digitizeddocument circulated to the user but also the state of another digitizeddocument not circulated to the user but having influence on the user'swork, so that the user can adjust the user's work correspondingly to theother work.

A second object of the present invention is that time, digitizeddocument name and user name can be provided as a transaction log inaddition to the first effect. The information concerning time, digitizeddocument name and user name is important in fulfilling the first effect.

A third effect of the present invention is that a transaction logcontaining a digitized document which is now not possessed by a userbecause it has been sent to the next user can be procured by the user sothat the state of progress of the transaction can be provided to theuser. The user can follow up other users by referring to the transactionlog.

A fourth effect of the present invention is that storage capacity can besaved by deleting the transaction log of a transaction when thecirculation of all digitized documents belonging to the transaction iscompleted. When the circulation of all digitized documents belonging tothe transaction is completed, the significance of the history of eachdigitized document is generally lowered, so that necessity of thetransaction log is reduced. Accordingly, the unnecessary transaction logcan be deleted so that storage capacity can be saved.

A fifth effect of the present invention is that transaction log data aredisplayed so as to be separated by digitized documents when atransaction log is displayed in a user terminal, so that the transactionlog in which a plurality of digitized documents and data concerningusers are mixed can be displayed so as to be easy to read. Thetransaction log is an information sequence concerning a plurality ofdigitized documents and user data belonging to one and the sametransaction. When a transaction is displayed in a user terminal, thetransaction log can be not only collectively displayed but alsodisplayed as auxiliary data while sorting the transaction log by usersor digitized documents. Accordingly, the users' understanding can behelped.

What is claimed is:
 1. A tangible medium storing a program executable by a sever to control transfer of a document among a plurality of computers, said program when executed causes said server to perform the steps of: storing, in a memory accessible by the server, a business process definition which is a circulation route of a document and which defines one of said computers as a transfer source computer of said document and another one of said computers as a transfer destination computer of said document, said business process definition having been predetermined prior to transfer of said document on said circulation route; transferring said document from said transfer source computer to said transfer destination computer based on said business process definition; creating, each time said document is transmitted from said transfer source computer to said transfer destination computer, transfer history information containing identifiers of said transfer source and transfer destination computers, a transfer time of said document, and an identifier of said document for every business process definition stored, and storing said transfer history information in said memory accessible by the server so as to be related to said business process definition according to related information; and responsive to a request including related information identifying desired transfer history information from a computer, extracting the requested transfer history information from said transfer history information stored in said memory based on said related information, and transmitting the extracted transfer history information to said computer which sent said request.
 2. The tangible medium storing a program according to claim 1, wherein said program when executed causes said server to further perform the steps of: outputting at least one of said transfer time, said identifier of said document, said identifier of said transfer source computer and the identifier of said transfer destination computer contained in said transfer history information to an external storage device.
 3. The tangible medium storing a program according to claim 1, wherein said program when executed causes said server to further perform the steps of: counting the number of times said document is transmitted to said transfer destination computer.
 4. The tangible medium storing a program according to 1, wherein said program when executed causes said computer to further perform the steps of: selecting, as the transmitting time of said transfer history information, at least one of Greenwich Mean Time (GMT), the local time where a computer is installed, and the local time of a designated area.
 5. The tangible medium storing a program according to claim 1, wherein said computer requesting said transfer history information is a computer other than said transfer source computer and said transfer destination computer.
 6. A tangible medium according to claim 1, wherein said server records one document and another document correlated with each other, receives a request for transfer history information and designation of said one document from a computer, and transmits to said computer requester in memory accessible by the server, transfer history information as to a transfer history of said another document which is correlated with said one document designated by said computer.
 7. A tangible medium according to claim 1, wherein said server records a plurality of documents and a transaction correlated with each other, receives a request for transfer history information and designation of a document from a computer, and transmits to said computer requested in memory accessible by the server, transfer history information including information of a history of said transaction which is correlated with said document designated by said computer.
 8. A tangible medium according to claim 1, wherein said related information related to said business process definition includes at least one of a user name, a transfer document name and a business process definition name.
 9. A tangible medium according to claim 1, wherein said related information related to said business process definition is a business process definition name, wherein transfer history information is extracted for each document to be transferred in a business process and the extracted transfer history information for each document is transmitted to said user terminal.
 10. A tangible medium according to claim 1, wherein the extracted transfer history information is displayed on a window for each related information related to said business process definition.
 11. A tangible medium according to claim 10, wherein when said transfer history information is displayed on the window for each related information related to said business process definition, a window displaying information of transfer history of an entire business process and a window displaying said transfer history information for each document to be transferred in said business process are displayed in corresponding relation to each other.
 12. A tangible medium storing a program executable by a server to control transfer of a document among a plurality of computers, said program when executed causes said server to perform the steps of: storing, in a memory accessible by the server, a business process definition which is a circulation route of a document and which defines one of said computers as a transfer source computer of said document and another one of said computers as a transfer destination computer of said document, said business process definition having been predetermined prior to transfer of said document on said circulation route; storing, in said memory accessible by the server, information of said transfer source and said transfer destination computers defined by said business process definition and transfer status information indicating a status and history of transfer of said document as said document is transferred between said transfer source and said transfer destination computers according to said business process definition; and indicating on a display information of said transfer source computer defined by said business process definition, said transfer destination computer defined by said business process definition, and transfer status information of a status and history of transfer of said document between said transfer source and said transfer destination computers defined by said business process definition.
 13. The server storing a program according to claim 12, wherein said program when executed causes said server to further perform the steps of: changing at least one of information indicating said transfer destination computer which received said document and information interconnecting said transfer source computer which transferred said document and said transfer destination computer.
 14. A tangible medium according to claim 12, wherein said server records one document and another document correlated with each other, receives a request for transfer history information and designation of said one document from a computer, and transmits to said computer requester in memory accessible by the server transfer history information as to a transfer history of said another document which is correlated with said one document designated by said computer.
 15. A tangible medium according to claim 12, wherein said server records a plurality of documents and a transaction correlated with each other, receives a request for transfer history information and designation of a document from a computer, and transmits to said computer requester in memory accessible by the server transfer history information including information of a history of said transaction which is correlated with said document designated by said computer.
 16. A tangible medium according to claim 12, wherein said related information related to said business process definition includes at least one of a user name, a transfer document name and a business process definition name.
 17. A tangible medium according to claim 12, wherein said related information related to said business process definition is a business process definition name, wherein transfer history information is extracted for each document to be transferred in a business process and the extracted transfer history information for each document is transmitted to said user terminal.
 18. A tangible medium according to claim 12, wherein the extracted transfer history information is displayed on a window for each related information related to said business process definition.
 19. A tangible medium according to claim 18, wherein when said transfer history information is displayed on the window for each related information related to said business process definition, a window displaying information of transfer history of an entire business process and a window displaying said transfer history information for each document to be transferred in said business process are displayed in corresponding relation to each other.
 20. A server apparatus for controlling transfer of a document among a plurality of computers, comprising: a memory which stores a business process definition which is a circulation route of a document and which defines one of said computers as a transfer source computer of said document and another one of said computers as a transfer destination computer of said document, said business process definition having been predetermined prior to transfer of said document on said circulation route; and a processing unit which transfers said document from said transfer source computer to said transfer destination computer based on said business process definition, creates, each time said document is transmitted from said transfer source computer to said transfer destination computer, transfer history information containing identifiers of said transfer source and transfer destination computers, a transfer time of said document and an identifier of said document for every business process definition stored in said memory, stores said transfer history information in said memory accessible by the server so as to be related to said business process definition according to related information and in response to a request for said transfer history information from a computer, extracts the requested transfer history information from said transfer history information stored in said memory based on said related information, and transmits said transfer history information to said computer which sent said request.
 21. The server apparatus according to claim 20, wherein said computer which requests said transfer history information is a computer other than said transfer source computer and said transfer destination computer.
 22. A server apparatus according to claim 20, wherein said server records one document and another document correlated with each other, receives a request for transfer history information and designation of said one document from a computer, and transmits to said computer requester in memory accessible by the server transfer history information as to a transfer history of said another document which is correlated with said one document designated by said computer.
 23. A server apparatus according to claim 20, wherein said server records a plurality of documents and a transaction correlated with each other, receives a request for transfer history information and designation of a document from a computer, and transmits to said computer requester in memory accessible by the server transfer history information including information of a history of said transaction which is correlated with said document designated by said computer.
 24. A server apparatus according to claim 20, wherein said related information related to said business process definition includes at least one of a user name, a transfer document name and a business process definition name.
 25. A server apparatus according to claim 20, wherein said related information related to said business process definition includes at least one of a user name, a transfer document name and a business process definition name.
 26. A server apparatus according to claim 20, wherein the extracted transfer history information is displayed on a window for each related information related to said business process definition.
 27. A server apparatus according to claim 26, wherein when said transfer history information is displayed on the window for each related information related to said business process definition, a window displaying information of transfer history of an entire business process and a window displaying said transfer history information for each document to be transferred in said business process are displayed in corresponding relation to each other.
 28. A server apparatus for controlling transfer of a document among of a plurality of computers, comprising: a memory which stores a business process definition which is a circulation route of a document and which defines one of said computers as a transfer source computer of a said document and another one of said computers as a transfer destination computer of said document, said business process definition having been predetermined prior to transfer of said document on said circulation route, and stores information of said transfer source and said transfer destination computers defined by said business process definition and transfer status information indicating a status and history of transfer of said document as said document is transferred between said transfer source and said transfer destination computers according to said business process definition; and a processing unit which indicates on a display information of said transfer source computer defined by said business process definition and said transfer destination computer defined by said business process definition, and transfer status information of a status and history of transfer of said document between said transfer source and said transfer destination computer defined by said business process definition.
 29. A server apparatus according to claim 28, wherein said server records one document and another document correlated with each other, receives a request for transfer history information and designation of said one document from a computer, and transmits to said computer requester in memory accessible by the server transfer history information as to a transfer history of said another document which is correlated with said one document designated by said computer.
 30. A server apparatus according to claim 28, wherein said server records a plurality of documents and a transaction correlated with each other, receives a request for transfer history information and designation of a document from a computer, and transmits to said computer requester in memory accessible by the server transfer history information including information of a history of said transaction which is correlated with said document designated by said computer.
 31. A server apparatus according to claim 28, wherein said related information related to said business process definition includes at least one of a user name, a transfer document name and a business process definition name.
 32. A server apparatus according to claim 28, wherein said related information related to said business process definition includes at least one of a user name, a transfer document name and a business process definition name.
 33. A server apparatus according to claim 28, wherein the extracted transfer history information is displayed on a window for each related information related to said business process definition.
 34. A server apparatus according to claim 33, wherein when said transfer history information is displayed on the window for each related information related to said business process definition, a window displaying information of transfer history of an entire business process and a window displaying said transfer history information for each document to be transferred in said business process are displayed in corresponding relation to each other.
 35. A digitized document circulation method of circulating a digitized document among a plurality of user terminals connected via a communication network, said digitized document circulating method comprising the steps of: sending, by a transmission source user terminal, a digitized document; delivering, by a server, said digitized document to a transmission destination user terminal, thereby circulating said digitized document according to a business process definition, said business process definition having been predetermined prior to transfer of said document on said circulation route; receiving, by said transmission destination user terminal, said digitized document; creating, by said server, a circulation history containing delivery time, an identifier of said digitized document, said transmission source user terminal and said transmission destination user terminal and storing said circulation history in said memory so as to be related to said business process definition according to related information; responding to a request, by a requester, said requester being a user terminal other than said transmission source and transmission destination user terminals, said request includes related information which identifies desired circulation history, extracting said circulation history from said circulation history stored in said memory based on said related information and transferring the extracted circulation history to said requester in response to a request for said circulation history issued from said user terminal other than said transmission source and transmission destination user terminals; and displaying said circulation history received by said requester on said user terminal other than said transmission source and transmission destination user terminals.
 36. A digital document circulation method according to claim 35, wherein said server records one document and another document correlated with each other, receives a request for transfer history information and designation of said one document from a computer, and transmits to said computer requester in memory accessible by the server transfer history information as to a transfer history of said another document which is correlated with said one document designated by said computer.
 37. A digital document circulation method according to claim 35, wherein said server records a plurality of documents and a transaction correlated with each other, receives a request for transfer history information and designation of a document from a computer, and transmits to said computer requester in memory accessible by the server transfer history information including information of a history of said transaction which is correlated with said document designated by said computer.
 38. A digitized document circulation method according to claim 35, wherein said related information related to said business process definition includes at least one of a user name, a transfer document name and a business process definition name.
 39. A digitized document circulation method according to claim 35, wherein said related information related to said business process definition is a business process definition name, wherein transfer history information is extracted for each document to be transferred in a business process and the extracted transfer history information for each document is transmitted to said user terminal.
 40. A digitized document circulation method according to claim 35, wherein the extracted transfer history information is displayed on a window for each related information related to said business process definition.
 41. A digitized document circulation method according to claim 40, wherein when said transfer history information is displayed on the window for each related information related to said business process definition, a window displaying information of transfer history of an entire business process and a window displaying said transfer history information for each document to be transferred in said business process are displayed in corresponding relation to each other.
 42. A computer program stored on a storage medium executable by a digitized document circulating system for circulating a digitized document among a plurality of user terminals connected via a communication network, said computer program when executed causes said digitized document circulating system to perform the steps of: sending, by a transmission source user terminal, a digitized document; delivering, by a server, said digitized document to a transmission destination user terminal, thereby circulating said digitized document according to a business process definition, said business process definition having been predetermined prior to transfer of said document on a circulation route; receiving, by said transmission destination user terminal, said digitized document; creating, by said server, a circulation history containing delivery time, an identifier of said digitized document, said transmission source user terminal and said transmission destination user terminal and storing said circulation history in said memory so as to be related to said business process definition according to related information; responding to a request, by a requester, said requester being a user terminal other than said transmission source and transmission destination user terminals, said request includes related information which identifies desired circulation history, extracting said circulation history from said circulation history stored in said memory based on said related information and transferring the extracted circulation history to said requester in response to a request for said circulation history issued from said user terminal other than said transmission source and transmission destination user terminals; and displaying said circulation history received by said requester on said user terminal other than said transmission source and transmission destination user terminals.
 43. A computer program according to claim 42, wherein said server records one document and another document correlated with each other, receives a request for transfer history information and designation of said one document from a computer, and transmits to said computer requester in memory accessible by the server transfer history information as to a transfer history of said another document which is correlated with said one document designated by said computer.
 44. A computer program according to claim 42, wherein said server records a plurality of documents and a transaction correlated with each other, receives a request for transfer history information and designation of a document from a computer, and transmits to said computer requester in memory accessible by the server transfer history information including information of a history of said transaction which is correlated with said document designated by said computer.
 45. A computer program according to claim 42, wherein said related information related to said business process definition includes at least one of a user name, a transfer document name and a business process definition name.
 46. A computer program according to claim 42, wherein said related information related to said business process definition is a business process definition name, wherein transfer history information is extracted for each document to be transferred in a business process and the extracted transfer history information for each document is transmitted to said user terminal.
 47. A computer program according to claim 42, wherein the extracted transfer history information is displayed on a window for each related information related to said business process definition.
 48. A computer program according to claim 47, wherein when said transfer history information is displayed on the window for each related information related to said business process definition, a window displaying information of transfer history of an entire business process and a window displaying said transfer history information for each document to be transferred in said business process are displayed in corresponding relation to each other.
 49. A method for utilizing transfer history information as to a digitized document in a server connected to a plurality of computers, said method comprising the steps of: managing, by said server, a business process definition having a plurality of transfer routes; recording, by said server in a memory accessible by said server, transfer history information as to a transfer history of document for each of said transfer routes so as to be related to said business process definition according to related information; receiving, by said server, a request for transfer of history information as to a document from a computer located on one transfer route; and in response to said request including related information identifying desired transfer history information, extracting the requested transfer history information from said transfer history information stored in said memory based on said related information, and transmitting, from said server to said computer issuing said request, the extracted transfer history information as to a document transferred on another transfer route other than said one transfer route, from among said transfer routes of said business process definition.
 50. A method according to claim 49, wherein said related information related to said business process definition includes at least one of a user name, a transfer document name and a business process definition name.
 51. A computer program according to claim 49, wherein said related information related to said business process definition is a business process definition name, wherein transfer history information is extracted for each document to be transferred in a business process and the extracted transfer history information for each document is transmitted to said user terminal.
 52. A computer program according to claim 49, wherein the extracted transfer history information is displayed on a window for each related information related to said business process definition.
 53. A computer program according to claim 52, wherein when said transfer history information is displayed on the window for each related information related to said business process definition, a window displaying information of transfer history of an entire business process and a window displaying said transfer history information for each document to be transferred in said business process are displayed in corresponding relation to each other. 